Add google_kms_key_ring_iam_policy resource and improve iam docs #814
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
google_kms_key_ring_iam_policy
.The first time I looked at managing IAM policy with Terraform, I was very confused about when to use the policy vs member vs binding resource. I tried to improve our docs by grouping them together on one page and try my best to explain the differences between each.
Please review carefully the proposed documentation change. If y'all agree on it. I will update the IAM docs for the other resource types following the same format.